Skip to content

Conversation

@gokuldharan-ni
Copy link
Collaborator

@gokuldharan-ni gokuldharan-ni commented Sep 12, 2025

Pull Request

🤨 Rationale

Task 3262819: Move the legacy variable query editor into v1 and add a new v2 variable query editor under feature toggle

This PR moves the legacy variable query editor into v1 and adds a v2 variable query editor under feature toggle.

👩‍💻 Implementation

  • Moves the legacy variable query editor into V1
  • Adds a new V2 variable query editor.
  • Adds a wrapper variable query editor that toggles v1 ad v2 based on feature toggle.

🧪 Testing

Added unit tests for the introduced functionalities

✅ Checklist

Gokuldharan added 4 commits September 18, 2025 12:59
Base automatically changed from users/Gokuldharan/split-v1-and-v2-components to main September 30, 2025 07:15
import { DataFrameVariableQueryEditorV1 } from './v1/DataFrameVariableQueryEditorV1';
import { DataFrameVariableQueryEditorV2 } from './v2/DataFrameVariableQueryEditorV2';

export function DataFrameVariableQueryEditorWrapper(props: Props) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: src/datasources/data-frame/components/DataFrameQueryEditorWrapper.tsx uses arrow function syntax. can we follow the same here to maintain consistency?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add tests for this file.

@richie-ni
Copy link
Collaborator

@gokuldharan-ni , When closing the PR, could we add a comment explaining the reason for closure so other reviewers can understand the context?

@gokuldharan-ni
Copy link
Collaborator Author

@gokuldharan-ni , When closing the PR, could we add a comment explaining the reason for closure so other reviewers can understand the context?

I have moved the changes to a different branch and created a PR for the other branch, so I abandoned this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants